-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(extensions): DataFilterExtension handling of filterSoftRange #8800
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A doc change warranted, or this is just an edge case?
Do we have a test harness?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it would be more efficient to keep the old shader and instead clip the value of the soft range in JS so it could never be in the wrong range
@ibgreen no doc change required, this is a bug fix @felixpalmer the issue here is when filter_min equals filter_softMin we still cannot use smoothstep. |
@Pessimistress I was suggesting we avoid |
If you look at the original issue, they are using filter_min == filter_softMin == filter_softMax == filter_max. It would not work with any modification. |
Closes #8774
Change List
filterSoftRange
is truncated byfilterRange
fallback to use hard edge